CVE-2023-52455
iommu: Don't reserve 0-length IOVA region
Description
In the Linux kernel, the following vulnerability has been resolved: iommu: Don't reserve 0-length IOVA region When the bootloader/firmware doesn't setup the framebuffers, their address and size are 0 in "iommu-addresses" property. If IOVA region is reserved with 0 length, then it ends up corrupting the IOVA rbtree with an entry which has pfn_hi < pfn_lo. If we intend to use display driver in kernel without framebuffer then it's causing the display IOMMU mappings to fail as entire valid IOVA space is reserved when address and length are passed as 0. An ideal solution would be firmware removing the "iommu-addresses" property and corresponding "memory-region" if display is not present. But the kernel should be able to handle this by checking for size of IOVA region and skipping the IOVA reservation if size is 0. Also, add a warning if firmware is requesting 0-length IOVA region reservation.
INFO
Published Date :
Feb. 23, 2024, 3:15 p.m.
Last Modified :
Nov. 21, 2024, 8:39 a.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | HIGH | [email protected] |
Solution
- Update the Linux kernel to a patched version.
- Reboot the system after the update.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2023-52455.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2023-52455 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2023-52455
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2023-52455 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2023-52455 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by af854a3a-2127-422b-91ae-364da2661108
Nov. 21, 2024
Action Type Old Value New Value Added Reference https://git.kernel.org/stable/c/5e23e283910c9f30248732ae0770bcb0c9438abf Added Reference https://git.kernel.org/stable/c/98b8a550da83cc392a14298c4b3eaaf0332ae6ad Added Reference https://git.kernel.org/stable/c/bb57f6705960bebeb832142ce9abf43220c3eab1 -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 28, 2024
Action Type Old Value New Value -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 14, 2024
Action Type Old Value New Value -
Initial Analysis by [email protected]
Apr. 30, 2024
Action Type Old Value New Value Added CVSS V3.1 NIST AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Changed Reference Type https://git.kernel.org/stable/c/5e23e283910c9f30248732ae0770bcb0c9438abf No Types Assigned https://git.kernel.org/stable/c/5e23e283910c9f30248732ae0770bcb0c9438abf Patch Changed Reference Type https://git.kernel.org/stable/c/98b8a550da83cc392a14298c4b3eaaf0332ae6ad No Types Assigned https://git.kernel.org/stable/c/98b8a550da83cc392a14298c4b3eaaf0332ae6ad Patch Changed Reference Type https://git.kernel.org/stable/c/bb57f6705960bebeb832142ce9abf43220c3eab1 No Types Assigned https://git.kernel.org/stable/c/bb57f6705960bebeb832142ce9abf43220c3eab1 Patch Added CWE NIST NVD-CWE-noinfo Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.3.0 up to (excluding) 6.6.14 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7.0 up to (excluding) 6.7.2 -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Feb. 23, 2024
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: iommu: Don't reserve 0-length IOVA region When the bootloader/firmware doesn't setup the framebuffers, their address and size are 0 in "iommu-addresses" property. If IOVA region is reserved with 0 length, then it ends up corrupting the IOVA rbtree with an entry which has pfn_hi < pfn_lo. If we intend to use display driver in kernel without framebuffer then it's causing the display IOMMU mappings to fail as entire valid IOVA space is reserved when address and length are passed as 0. An ideal solution would be firmware removing the "iommu-addresses" property and corresponding "memory-region" if display is not present. But the kernel should be able to handle this by checking for size of IOVA region and skipping the IOVA reservation if size is 0. Also, add a warning if firmware is requesting 0-length IOVA region reservation. Added Reference Linux https://git.kernel.org/stable/c/98b8a550da83cc392a14298c4b3eaaf0332ae6ad [No types assigned] Added Reference Linux https://git.kernel.org/stable/c/5e23e283910c9f30248732ae0770bcb0c9438abf [No types assigned] Added Reference Linux https://git.kernel.org/stable/c/bb57f6705960bebeb832142ce9abf43220c3eab1 [No types assigned]